1. Data files from ImQMD
	INPUT.DAT contains information about the simulation
	OUTPUT3.DAT contains the information that needs to go into gemini, but the form is not correct. 
	Original data files can be found here: /evtdata/AMD2005-tmp/ImQMD06/zhyx/ . 
	Other data files are located in our event space: /evtdata/EOS_sim-3/BUU/vredevoo/data and /evtdata/EOS_sim-3/BUU/mosbym/data 

2. Copy the following directories: /evtdata/EOS_sim-3/BUU/mosbym/exen/ and /evtdata/EOS_sim-3/BUU/mosbym/gem/

3. Exen.f
	Zhang's script that takes the raw ImQMD and formats it for input into gemini. The script does not need to be compiled, but if 
	you make changes, it was compiled using ifort.  The script is in the exen directory. The OUTPUT3.DAT and INPUT.DAT files that 
	you wish to format must be copied into the exen directory. Then, run the executable by typing ./a.out. When it asks for the 
	name of the file, type OUTPUT3.DAT.
	This produces a file called table21.dat:
	z n px py pz E Jx Jy Jz b ev.
	z = proton number
	n = neutron number
	pi = momentum components
	E = total energy (to which gemmonte adds the binding energy)
	Ji = spin components (not treated by ImQMD - all zeros)
	b = related to impact parameter (not used by gemini but it does keep track of this)
	ev = event number that the fragment comes from.

4. Gemini
	Move the table21.dat file to the gem directory.
	Gemmonte is the program you need to run. If you need to recompile, type make gemmonte in the gemini directory.
	In gem_kind.f90, make sure PARAMETER gemini_home lists the path to the directory you've placed gemini in.
	To run gemini, type ./gemmonte. You have to enter information, so it can't be run in the background. The input 
	file is table21.dat, from step 3. It will also ask for the name of an output file, which should be of thie form: sn124E50b2g05.dat. 
	Run one monte carlo event.

5. gem2py.cc
	This program changes the output from gemini to be in the pythia output format, which is required for GEANT. In the file, the input 
	and output file names need to be changed. check to make sure the system information is correct, including target, projectile, 
	and energy.
	This program is compiled using g++.
	Finally, run the executable.
	The heavier fragments don't have PDG codes, so they have the following convenction: 10000000000 + z*10000+n*10, but these are not
 	currently recognized in GEANT

	Format:
	status PID parent daughter px py pz E
	status = particle status (1)
	PID = PDF particle ID
	parent = parent line number (set to 0 in our case)
	daugher = first daughter line number (set to 0 in our case)
	pi = GeV/c
	E = GeV

